Received: from alaska.et.byu.edu by darth.byu.edu (NX5.67d/NX3.0M)
id AA00486; Sun, 3 Jul 94 20:03:12 -0600
Received: from yvax1.byu.edu by alaska.et.byu.edu; Sun, 3 Jul 1994 18:36:03 -0600
Received: from DIRECTORY-DAEMON by yvax.byu.edu (PMDF V4.3-7 #7277)
id <01HEA2OU7QFK0Q80TJ@yvax.byu.edu>; Sun, 3 Jul 1994 18:35:44 MDT
Received: from alaska.et.byu.edu by yvax.byu.edu (PMDF V4.3-7 #7277)
id <01HEA2ORSVA8HTTJR9@yvax.byu.edu>; Sun, 3 Jul 1994 18:35:40 MDT
Received: from yvax1.byu.edu by alaska.et.byu.edu; Sun,
3 Jul 1994 18:35:08 -0600
Received: from DIRECTORY-DAEMON by yvax.byu.edu (PMDF V4.3-7 #7277)
id <01HEA2NMWU0G0Q80TJ@yvax.byu.edu>; Sun, 3 Jul 1994 18:34:46 MDT
Received: from mimbres.cs.unm.edu by yvax.byu.edu (PMDF V4.3-7 #7277)
id <01HEA2NJSZLSHTS8XP@yvax.byu.edu>; Sun, 3 Jul 1994 18:34:42 MDT
Received: by mimbres.cs.unm.edu (5.65/033093)
with UUCP id <AA12746@mimbres.cs.unm.edu>; Sun, 3 Jul 94 18:20:20 -0600
Received: from goat (goat [192.54.108.9]) by droid (8.6.7/8.6.6)
with SMTP id SAA22961; Sun, 3 Jul 1994 18:16:37 -0600
Received: by goat (NX5.67d/NX3.0X) id AA00298; Sun, 3 Jul 94 18:16:36 -0600
Received: by NeXT.Mailer (1.100)
Received: by NeXT Mailer (1.100)
Date: Sun, 03 Jul 1994 18:16:36 -0600
From: Andrew Stone <andrew@stone.com>
Subject: Re: Foundation and Misc
To: Bruce McKenzie <bruce@trwlasd.com>
Cc: misckit@byu.edu, miscstring@byu.edu
Message-Id: <199407040016.SAA22961@droid>
Content-Transfer-Encoding: 7BIT
Bruce is right about needing both MiscString and MiscStringNew (although, I'd propose we move to a new prefix MOSString (Misc OpenStep String).
One reason you can't just rename is that folks may need to unarchive MiscString, so we'll need a core MiscString with read: and write: minimally.
Begin forwarded message:
Date: Sun, 03 Jul 1994 14:17:51 -0700
From: Bruce McKenzie <mimbres!trwlasd.com!bruce>
Subject: Re: Foundation and Misc
To: tsengel@cip.informatik.uni-erlangen.de
Cc: misckit@byu.edu, miscstring@byu.edu
Content-Transfer-Encoding: 7BIT
> MiscString.... Hmm ok what about making it a subclass of
> NSString an add the missing methods + maybe some
> compatibility stuff for the first time. If the MiscKit would
> define a dummy NSString tomorrow we could start switching to
> the NSString where sufficient. And places that need more
> functionallity could be converted to Misc .... and would
> remain Misc in 4.0. It would be nice to use NSString really
> soon because methods should use it heavily for casting. If we
> have it all Misc.. We can distinguish later where NSString is
> sufficient and where MiscString really is required as an
> argument.
I'd recommend a different approach. Define a new class 'MiscStringNew' (excuse me, I'm onomatopoetically challenged) that is the subclass of NSString. Add the behaviour to it, and allow MiscString to wither (bug fixes only) until the world is using MiscStringNew.
I think a critical part of this migration is the separation and refinement of the API. Currently, MiscString is a kitchen sink of a class. There's a lot of great stuff there, but it is neither complete nor consistent in its offerings (e.g. you can search for chars in 37,000,000 ways, but there is limited support for *non regex* string searching).
Bruce
---
Bruce McKenzie (spuds@netcom.com, NeXTMail welcome)
Atlas Software Ventures, Inc.
PO Box 1299, Santa Clara, CA 95052-1299
800/278-9909 (ASV-9909)
*** Software Development, specializing in NEXTSTEP ***
